I prefer not to merge this one as it goes a bit to far in code reduction with several fallbacks :

• min_size is not set per binary any more
• 1.6.0+updateXX seems to be the Debian scheme and I want to keep this scripts with the one I use in the debian Java-package.
• I'm not sure BASH_REMATCH works with dash and I would like to keep this as a goal
• Code is longer but clearer the way it was, easier to add new entries to (my feeling)

I'll fix the two digit Java 7 update with a great duplication of entries :-)

• How is determined min_size? Could it be computed with the size of the archive instead of hardcoding the value in the script?
• Regarding the version, I simply followed the scheme of the sun-java6 package. Since the packages generated by java-package will most probably replace sun-java6 I think it's wise to follow this pattern.
• I confirm BASH_REMATCH doesn't work with dash, however there are other bashisms that prevent the script from running with dash. I thought that was ok as long as the generated packages can be installed with dash.
• The purpose of the patch is to not add new entries in the future, it could work with jdk10u23 in 15 years ;)

• Yes it probably can. It's approximately the size of expanded binary archive. The goal is just to check disk space.
• It could. After all, current java-package output is not compliant with openjdk scheme on Debian neither..
• Well, it's a goal, I know it's not dash compliant right now.
• Oh yes, I didn't notice that :-/ !
  Ok then, let's go. I'll see what can fit in the Debian packaged version later.